npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

is-cross-origin

v1.0.1

Published

tells whether provided window is cross origin or same origin

Downloads

2,380

Readme

is-cross-origin

a simple API for telling whether a window is cross origin or same origin

install

yarn add is-cross-origin / npm install is-cross-origin

usage

the API should be provided with one/two arguments, both windows. the first is a destination window to test its origin in relation to a source window, and the second is that source window. second argument is optional, and will be set to current window in case not provided.

const isCrossOrigin = require('is-cross-origin');
const result = isCrossOrigin(dstWindow, srcWindow);
if (result) {
    console.log('destination window ', dstWindow, ' is in a cross origin in relation to source window ', srcWindow);
} else {
    console.log('destination window ', dstWindow, ' is in the same origin as the source window ', srcWindow);
}

so for example, in order to tell whether a certain iframe is in a cross origin in relation to the current window, this should do the trick:

<html>
    <head></head>
    <body>
        <iframe id="a" src="/"></iframe>
        <iframe id="b" src="//cross-origin.com"></iframe>
        <script>
            window.onload = function() {
                const aIsCrossOrigin = isCrossOrigin(a.contentWindow /*, window*/);
                const bIsCrossOrigin = isCrossOrigin(b.contentWindow /*, window*/);
                console.log('is "a" cross origin? ' + aIsCrossOrigin); // false
                console.log('is "b" cross origin? ' + bIsCrossOrigin); // true
            }
        </script>
    </body>
</html>

usage update

now a third argument can be passed that will be the Object constructor to use when telling whether provided arguments are of type windows or not (default will evaluate to window.Object:

isCrossOrigin(dstWindow, srcWindow, window.Object /* optional */)

important usage notes

  • window should finish loading in order for this API to work. if the API is provided with a window that did not finish loading, it will return false regardless of whether the iframe is cross origin or not. to avoid that, call the API with windows that finished loading by using onload event handler or something similar.

compatibility

compatibility table